PR Update

• Move Yaml validator out of Persistence again with the existing refactoring updates. As Persistence uses .net8 , while pac supports several other .net verisons.
• The intention is to still package YamlValidator into a separate NuGet package from Persistence (due to compatbility issues with PAC CLI). The build process of signing this binary and adding it to the build pipeline will be done in a separate pr.

Problem

• At it's current state, the YamlValidator can't be properly consumed by pac CLI to perform validation
• This re-write fixes that with a factory class to build validators (which can be extended if need be in the future)

Notes

• The factory for the Validator is barebones, however some extensions that can be made using the factory include:
  • passing in options to produce errors in different languages: https://docs.json-everything.net/schema/basics/#schema-error-localization
  • Passing in parameters to output raw json schema evaluation results to feed into other programs or for internal use
  • passing in parameters to clarify schema spec (ex: 2020-12) used by json schema
• Error handling:
  • The Validator will gracefully handle any errors that involve edge cases when validating yaml strings (empty, not yaml etc) as well as any issues with the schema in the nuget package
• File I/O error will always be handled by pac cli

Validation

• Unit tests
• Added unit test for factory class as well

Schema Loading

• Instead of using file I/O and building to a local directory, schemas are built into the assembly itself , subschemas and schemas are then loaded into memory, like bolt.module.connector does